UCF STIG Viewer Logo
Changes are coming to https://stigviewer.com. Take our survey to help us understand your usage and how we can better serve you in the future.
Take Survey

The router must be configured to only permit management traffic that ingresses and egresses the OOBM interface.


Overview

Finding ID Version Rule ID IA Controls Severity
V-78351 SRG-NET-000205-RTR-000012 SV-93057r2_rule Medium
Description
The OOBM access switch will connect to the management interface of the managed network elements. The management interface can be a true OOBM interface or a standard interface functioning as the management interface. In either case, the management interface of the managed network element will be directly connected to the OOBM network. An OOBM interface does not forward transit traffic, thereby providing complete separation of production and management traffic. Since all management traffic is immediately forwarded into the management network, it is not exposed to possible tampering. The separation also ensures that congestion or failures in the managed network do not affect the management of the device. If the device does not have an OOBM port, the interface functioning as the management interface must be configured so that management traffic does not leak into the managed network and that production traffic does not leak into the management network.
STIG Date
Router Security Requirements Guide 2019-03-20

Details

Check Text ( C-77911r2_chk )
Step 1: Verify that the managed interface has an inbound and outbound ACL configured.

Step 2: Verify that the ingress filter only allows management, IGP, and ICMP traffic.

Caveat: If the management interface is a true OOBM interface, this requirement is not applicable.

If the router does not restrict traffic that ingresses and egresses the management interface, this is a finding.
Fix Text (F-85081r2_fix)
If the management interface is a routed interface, it must be configured with both an ingress and egress ACL.